refactor: 容器注解补 Any 参数 + 移除 reportMissingTypeArgument 全局抑制 - #3

Please address the comments from this code review:

## Overall Comments
- The ad-hoc `_to_int` helpers introduced in `floating_state.py` and `window_snap.py` are identical; consider centralizing this logic (and similar JSON numeric normalization) in a shared utility to avoid duplication and keep behavior consistent.
- Now that `JsonObject` and `MeasureState` are introduced, you might want to scan for remaining dynamic-JSON `dict[str, Any]` usages and align them with these aliases to make the typing boundary even clearer and more uniform.
- In `detect_negative_cost` the extra `white_rows` cast and index-based loop add complexity; you could iterate directly over `white` (with an explicit `np.ndarray` annotation) to keep the code simpler while still satisfying strict type checking.

## Individual Comments

### Comment 1
<location path="aao/ui/floating_state.py" line_range="61-62" />
<code_context>
     if not isinstance(g, list | tuple):
         return
-    x, y, w, h = [int(v) for v in g]
+    values = [_to_int(v) for v in cast(list[object] | tuple[object, ...], g)]
+    x, y, w, h = values
     widget.setGeometry(x, y, w, h)

</code_context>
<issue_to_address>
**issue (bug_risk):** Restore geometry should guard against sequences with length != 4 to avoid runtime errors.

`restore_geometry` only checks that `g` is a list/tuple, not that it has length 4. If stored geometry has a different length (e.g., corrupted settings), `x, y, w, h = values` will raise `ValueError`. Please reuse `_valid_geometry` (or at least its length check) before unpacking so invalid data is skipped instead of crashing.
</issue_to_address>

### Comment 2
<location path="aao/resources/updater.py" line_range="98-99" />
<code_context>
                 req.add_header("Authorization", f"Bearer {token}")
             with urllib.request.urlopen(req, timeout=10) as resp:
-                data = json.loads(resp.read())
+                raw = json.loads(resp.read())
+                data = cast(JsonObject, raw) if isinstance(raw, dict) else {}
         except Exception as e:  # noqa: BLE001
             logger.warning("检查更新失败: %s", e)
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Unexpected response shapes from GitHub are silently treated as empty dict, which can hide issues.

When GitHub returns a non-dict payload (e.g., error JSON or HTML), `raw` is discarded and `data` becomes `{}` with no extra logging, so callers just see “no update” instead of a failed check. Consider logging a warning when `raw` is not a dict (or returning `None`) so the failure is visible to callers.

Suggested implementation:

```python
            if token:
                req.add_header("Authorization", f"Bearer {token}")
            with urllib.request.urlopen(req, timeout=10) as resp:
                raw = json.loads(resp.read())
                if isinstance(raw, dict):
                    data = cast(JsonObject, raw)
                else:
                    logger.warning("检查更新失败，返回 payload 非 JSON 对象: %r", raw)
                    return None
        except Exception as e:  # noqa: BLE001
            logger.warning("检查更新失败: %s", e)
            return None

```

```python
        try:
            req = _make_request(_RELEASES_LIST_API, _settings_github_token())
            with urllib.request.urlopen(req, timeout=10) as resp:
                raw = json.loads(resp.read())
                if isinstance(raw, list):
                    releases = cast(list[JsonObject], raw)
                else:
                    logger.warning("拉取 release 列表失败，返回 payload 非 JSON 数组: %r", raw)
                    return ""
        except Exception as e:  # noqa: BLE001
            logger.warning("拉取 release 列表失败，降级为单版 changelog: %s", e)
            return ""

```
</issue_to_address>